home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group98b.txt
/
000001_icon-group-sender _Mon Apr 27 08:07:35 1998.msg
< prev
next >
Wrap
Internet Message Format
|
2000-09-20
|
5KB
Return-Path: <icon-group-sender>
Received: from kingfisher.CS.Arizona.EDU (kingfisher.CS.Arizona.EDU [192.12.69.239])
by baskerville.CS.Arizona.EDU (8.8.8/8.8.7) with SMTP id IAA17994
for <icon-group-addresses@baskerville.CS.Arizona.EDU>; Mon, 27 Apr 1998 08:07:35 -0700 (MST)
Received: by kingfisher.CS.Arizona.EDU (5.65v4.0/1.1.8.2/08Nov94-0446PM)
id AA07928; Mon, 27 Apr 1998 08:07:32 -0700
Message-Id: <3.0.5.32.19980424030719.007b7960@doors>
X-Sender: bgbauer#alpha.delta.edu@doors
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32)
Date: Fri, 24 Apr 1998 03:07:19 -0700
To: "Icon Group"<icon-group@optima.CS.Arizona.EDU>
From: Scissors <bgbauer@alpha.delta.edu>
Subject: Re: Win32 API support for Icon
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Errors-To: icon-group-errors@optima.CS.Arizona.EDU
Status: RO
Content-Length: 4187
Hello,
Thanks for all the replys. Im new to the group, so I hope I havent
brought up a topic that has been over talked. Im glad people have shown
interest though. I've been feeling quite stranded since I began looking
for a compiler. (Is Icon considered a full fledged compiler? Or is the
interpreter just stacked into that 175K that my tiny programs seem to take
up?) Once I decided to try out Icon I felt even more alone. Which is sad,
because as I said previously, I like the language. If I keep up with Icon.
(I plan to for atleast a few small programs, or until I hit a real
'Limitation'.)
So let me clear up my original post. Im not really looking for the full
win32 api. Just a few 'key' elements (explained further down).
Anyway, all I was really wondering was if there were ways to do what
C/C++ programs can do in windows. I cant afford Borland or VC++ and the
books it would take to delve into C/C++. Im not even sure if I want to
invest that amount of time. So I cant really learn a few of the
suggestions that were made. It would be too frustrating and confusing at
this point.
All I was "hoping" there was, was a few ways to interface with (Im sure
every one has a different opinion on this) but 'key' elements of the
windows interface. The registry, where my current project needs to obtain
information. (As will a future project I am planning). The registry is
actually one of my biggest limits. I feel like its 'key' because much of
windows 'look and feel' is stored there in settings. If I could read the
registry, I could find the users preferred 'edit area font' and 'text
color', all of the users preferences I could know without the user needing
to set them. I could read Ole settings to know what programs open what
types of documents. (Useful if say I wrote an HTML editor, and wanted to
be able to allow them to browse the document. (of course I can just do this
with system("Start newfile.html").
My current project involves reading in a serialized index file. Now, if
I could read the registry, I could easily know exactly where the program
that created it, and the file itself, is located on disk, without needing
to prompt the user. The path to the file, is already stored in the
registry. This doesnt apply so much to the older win3.1, but both win95/NT
maintain a registry. Its a key element to the O/S.
Im guessing this ability is already included in Icon, because of Icons
use of the File Open, Font Selection, Color Selection dialogues matching
the 'look and feel' of Windows. The ability to interface Windows API, I
mean. Maybe Im confused, but couldnt Icon offer a 'pass through' type of
call which allows calling most WinAPI functions?
Like I said, Im new to this, so maybe that is harder to implement than I am
realising. But that is what I was really seeking.
This may be what one of the replys what trying to point out, when it
mentioned a need for a DLL Guru. An MFC*.dll guru. Who could create the
interface.
I realise Icon is a free research langauge, and that its portability is
of concern. I just was interested in knowing how far Icon can stretch.
So... Ive written a ReadIni(), and WriteIni() procedure. Im putting
together an iowin.icn Procedure file, for anyone interested. Mostly its
stuff that I needed, that wasnt in io.icn, or that the io.icn version didnt
seem to handle correctly for windows based systems. Im currently creating
a Registry procedure also. Ive got to rework it though because of limits I
found where calls to system() which create files (or atleast a call to
regedit) dont appear to be releasing the files before system() returns.
It's just a "work-around", and im not sure writing to the registry in this
manner would be %100 safe, which is why I wish I could do it correctly.
I'll find out in implementing it though. Other than the bug with 'repeated
reads' I Can read the registry now. If you're interested in this, let me
know. I'd like to know how many more of you out there are working on
win95/nt. And what procedures you may have created which are win95/nt based.
bgbauer
(My originally post was via usenet 'AKA' Mr Plow).